6 sessions on compose multiplatform with a coding agent: the agent failed at least once in 4, and 2 finished without a human stepping in.
Takeaway: Next time I'd point straight at the ICloudBackupTransport file since the crash log made the source pretty obvious, and let the agent confirm the main-thread-blocking theory with a quick web search before touching code.
Takeaway: Next time I'd start with the exact repro steps (stay-on-Home vs navigate-into-account) up front, since the vague first description led to two wrong fixes before the real bug surfaced.
Takeaway: I'd tell it up front which files/paths are likely stale so it doesn't waste turns hitting ENOENT on renamed importer adapters and onboarding files — that was the main friction.
Takeaway: Next time I'd just say upfront that the picker needs to work on Android, iOS and Web too, not just desktop — that would have saved a whole extra research and implementation pass.
Takeaway: I'd start the next session by pointing straight at the plan file and the exact behavior I want (like I did with the CancellationException bug report), since giving the agent the precise symptom and fix upfront meant it found the bug fast and fixed it correctly first try.
Takeaway: I'd start by naming the provider metadata type up front (BackupProvider, not BackupProviderInfo) so I wouldn't need a follow-up rename pass across sharedLib, composeApp and cliApp plus a second commit and ABI re-check.